User interface for a flashlight mode on an electronic device

ABSTRACT

An electronic device having a touch-screen display detects a first input on the display while displaying a first user interface on the display. In response to detecting the first input on the display, the device enters a flashlight mode. Entering the flashlight mode includes replacing the first user interface with a first flashlight user interface. The first flashlight user interface has a first total lumen output and a first luminance that is substantially uniform over the display. The device determines whether brightness change criteria are met, and in accordance with a determination that the brightness change criteria are met, displays a second flashlight user interface having a second total lumen output greater than the first total lumen output and a second luminance that is substantially uniform over the display.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/791,829, entitled “USER INTERFACE FOR A FLASHLIGHT MODE ON ANELECTRONIC DEVICE”, filed on Oct. 24, 2017, which claims priority toU.S. provisional patent application 62/506,866, entitled “USER INTERFACEFOR A FLASHLIGHT MODE ON AN ELECTRONIC DEVICE”, filed on May 16, 2017,the contents of which are hereby incorporated by reference in theirentirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for providing a flashlight mode onan electronic device.

BACKGROUND

Many modern electronic devices are capable of detecting user inputs andinclude a display that emits visible light. In some devices, the displayis sensitive to touch inputs. There is therefore an opportunity to usethe input detection and display capability of such electronic devices toimplement and control various applications that involve the emission ofvisible light.

BRIEF SUMMARY

Some devices include a dedicated light source (e.g., an LED, light bulb,camera flash, blinker, or the like) that can serve as a flashlight forilluminating the environment surrounding the device or drawing attentionto the device (e.g., as a safety light, for example, for making driversaware of the presence of a biker or jogger wearing or holding thedevice). Other devices do not include a dedicated light source, but havea display that emits visible light. Some techniques for operating thedisplay, however, are generally not suitable and inefficient as aflashlight (e.g., for providing illumination so that a user can see asurrounding environment or for drawing attention to the device).

Accordingly, the present technique provides electronic devices with moreeffective and efficient methods and interfaces for implementing aflashlight mode using a display of the electronic device. Such methodsand interfaces optionally complement or replace other methods forproviding a flashlight mode. Such methods and interfaces reduce thecognitive burden on a user and produce a more efficient human-machineinterface. For battery-operated computing devices, such methods andinterfaces conserve power and increase the time between battery charges.

In some embodiments, a method is performed at an electronic device witha touch-sensitive display. While displaying a first user interface onthe display, a first input on the display is detected. In response todetecting the first input on the display, a flashlight mode is entered.Entering the flashlight mode includes replacing the first user interfacewith a first flashlight user interface. The first flashlight userinterface has a first total lumen output and a first luminance that issubstantially uniform over the display. A determination is made whetherbrightness change criteria are met. In accordance with a determinationthat the brightness change criteria are met, a second flashlight userinterface is displayed. The second flashlight user interface having asecond total lumen output greater than the first total lumen output anda second luminance that is substantially uniform over the display.

In some embodiments, a non-transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of an electronic device with a touch-sensitive display. Theone or more programs include instructions for: while displaying a firstuser interface on the display, detecting a first input on the display;in response to detecting the first input on the display, entering aflashlight mode, where entering the flashlight mode includes replacingthe first user interface with a first flashlight user interface, thefirst flashlight user interface having a first total lumen output and afirst luminance that is substantially uniform over the display;determining whether brightness change criteria are met; and inaccordance with a determination that the brightness change criteria aremet, displaying a second flashlight user interface, the secondflashlight user interface having a second total lumen output greaterthan the first total lumen output and a second luminance that issubstantially uniform over the display.

In some embodiments, a transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of an electronic device with a touch-sensitive display. Theone or more programs include instructions for: while displaying a firstuser interface on the display, detecting a first input on the display;in response to detecting the first input on the display, entering aflashlight mode, where entering the flashlight mode includes replacingthe first user interface with a first flashlight user interface, thefirst flashlight user interface having a first total lumen output and afirst luminance that is substantially uniform over the display;determining whether brightness change criteria are met; and inaccordance with a determination that the brightness change criteria aremet, displaying a second flashlight user interface, the secondflashlight user interface having a second total lumen output greaterthan the first total lumen output and a second luminance that issubstantially uniform over the display.

In some embodiments, an electronic device includes a touch-sensitivedisplay, one or more processors, and memory. The memory stores one ormore programs configured to be executed by the one or more processors.The one or more programs including instructions for: while displaying afirst user interface on the display, detecting a first input on thedisplay; in response to detecting the first input on the display,entering a flashlight mode, where entering the flashlight mode includesreplacing the first user interface with a first flashlight userinterface, the first flashlight user interface having a first totallumen output and a first luminance that is substantially uniform overthe display; determining whether brightness change criteria are met; andin accordance with a determination that the brightness change criteriaare met, displaying a second flashlight user interface, the secondflashlight user interface having a second total lumen output greaterthan the first total lumen output and a second luminance that issubstantially uniform over the display.

In some embodiments, an electronic device includes: a touch-sensitivedisplay; means for while displaying a first user interface on thedisplay, detecting a first input on the display; means for, in responseto detecting the first input on the display, entering a flashlight mode,where entering the flashlight mode includes replacing the first userinterface with a first flashlight user interface, the first flashlightuser interface having a first total lumen output and a first luminancethat is substantially uniform over the display; means for determiningwhether brightness change criteria are met; and means for, in accordancewith a determination that the brightness change criteria are met,displaying a second flashlight user interface, the second flashlightuser interface having a second total lumen output greater than the firsttotal lumen output and a second luminance that is substantially uniformover the display.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for providing a flashlight mode on an electronic device,thereby increasing the effectiveness, efficiency, and user satisfactionwith such devices. Such methods and interfaces may complement or replaceother methods for providing a flashlight mode on an electronic device.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 6A-6AG illustrate exemplary user interfaces in accordance withsome embodiments.

FIGS. 7A-7D are a flow diagram illustrating a method for operating anelectronic device in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for implementing a flashlight mode on an electronicdevice. In one example, a device provides a flashlight mode thatdisplays a first flashlight user interface with a reduced or dimmedbrightness. The dimmed interface provides a comfortable brightness levelwhile the user views indications on the display about how to operate theflashlight mode and interacts with the display (e.g., to adjustcharacteristics of the flashlight mode). In accordance with adetermination that certain criteria are met, the device transitions to asecond flashlight user interface with an increased brightness thatserves as a flashlight. Such techniques can reduce the cognitive burdenon a user who accesses a flashlight mode on an electronic device,thereby enhancing productivity. Further, such techniques can reduceprocessor and battery power otherwise wasted on redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description ofexemplary devices for performing the techniques for providing aflashlight mode on a display of an electronic device. FIGS. 6A-6AGillustrate exemplary user interfaces for a flashlight mode. FIGS. 7A-7Dare a flow diagram illustrating methods of providing a flashlight modein accordance with some embodiments. The user interfaces in FIGS. 6A-6AGare used to illustrate the processes described below, including theprocesses in FIGS. 7A-7D.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.1 in,and/or IEEE 802.1 lac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer (notshown) and a GPS (or GLONASS or other global navigation system) receiver(not shown) for obtaining information concerning the location andorientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data: calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo!Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video,”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including process 700 (FIGS.7A-7D). A computer-readable storage medium can be any medium that cantangibly contain or store computer-executable instructions for use by orin connection with the instruction execution system, apparatus, ordevice. In some examples, the storage medium is a transitorycomputer-readable storage medium. In some examples, the storage mediumis a non-transitory computer-readable storage medium. The non-transitorycomputer-readable storage medium can include, but is not limited to,magnetic, optical, and/or semiconductor storages. Examples of suchstorage include magnetic disks, optical discs based on CD, DVD, orBlu-ray technologies, as well as persistent solid-state memory such asflash, solid-state drives, and the like. Personal electronic device 500is not limited to the components and configuration of FIG. 5B, but caninclude other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “IT_(L)”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“IT_(D)”) in FIG. 5H. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT_(D)”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “IT_(D)”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “IT_(D)”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6AG illustrate exemplary user interfaces for operating anelectronic device in a flashlight mode, in accordance with someembodiments. The user interfaces in these figures are used to illustratethe processes described below, including the processes in FIGS. 7A-7D.

FIG. 6A illustrates device 600 with touch-sensitive display 602. Device600 may be device 100, 300, or 500 in some embodiments. Optionally,device 600 includes an orientation sensor configured to detect aphysical orientation of device 600. Optionally, device 600 includes anattachment mechanism configured to attach device 600 to a user's wrist.User interface 610 is displayed on touch-sensitive display 602. Userinterface 610, includes watch face 611. In some embodiments, userinterface 610 includes a user interface for an application or anapplication springboard that includes a plurality of affordances (e.g.,a menu) for launching respective applications.

Device 600 includes various input mechanisms that receive user input,such as, rotatable input mechanism 604, that is able to receive arotatable input (and may also receive a push input), and input mechanism606 that is able to receive a push user input.

In response to detecting input 650 (e.g., an upward swipe shown in FIG.6A) on touch-sensitive display 602, device 602 displays user interface620 for a Control Center, which includes a plurality of affordances621-626 corresponding to various respective features of device 600(e.g., power settings, alarm settings, airplane mode, sleep mode), asshown in FIG. 6B. While displaying user interface 620, device 600detects input 651 on display 602. Input 651 corresponds to selection offlashlight affordance 626 for activating a flashlight mode on device600. The flashlight mode displays user interfaces on display 602 thatcan be used to illuminate the surrounding environment with light emittedfrom display 602. The flashlight mode thus enables device 600 to serveas a flashlight using the light emitted from display 602, even if device600 does not include another light source capable of providingillumination. The features described below allow device 600 to be usedas a flashlight in an intuitive, efficient, and user-friendly manner.

Device 600 enters the flashlight mode in response to detecting input651. As shown in FIGS. 6C-6D, entering the flashlight mode includesreplacing user interface 620 with a first flashlight user interface 630.In one example, device 600 transitions to first flashlight userinterface 630 by animating first flashlight user interface 630translating upward onto display 602 from the bottom edge of display 602.FIG. 6C illustrates the transition between the display of user interface620 in FIG. 6B and the display of first flashlight user interface 630 inFIG. 6D. Optionally, first flashlight user interface 630 at leastinitially includes a dismiss affordance 631 for dismissing theflashlight mode, as shown at the top of display 602 in FIG. 6D. In someembodiments, dismiss affordance 631 is displayed somewhere other than atthe top of display 602 (e.g., at the bottom, side, or center of display602).

As shown in FIG. 6D, first flashlight user interface 630 includesflashlight style indicia 632, which indicate a sequence of flashlightstyles. Exemplary flashlight styles will be described in greater detailbelow. For now, flashlight style indicia 632 include dots 632-1, 632-2,and 632-3 corresponding to respective flashlight styles. Flashlightstyle indicia 632 provide visual feedback to the user that there arethree available flashlight styles arranged in a horizontal sequence(based on the orientation of device 600 in FIG. 6D). Flashlight styleindicia 632 include an indication 633 of the flashlight style accordingto which the flashlight mode is currently operating. In FIG. 6D,indication 633 indicates that the current style corresponds to the leftdot 632-1, and therefore, is the first or far left flashlight style inthe sequence.

In some embodiments, dismiss affordance 631 is removed from firstflashlight user interface 630 after a predetermined amount of time. Insome embodiments, dismiss affordance 631 is removed in response to aninput (e.g., a tap or upward swipe on display 602). As shown in FIG. 6E,dismiss affordance 631 is removed and an indication of time 634 isdisplayed.

Referring further to FIG. 6E, scale 660 represents the brightness oramount of visible light output by display 602 when displaying firstflashlight user interface 630 in FIG. 6E. In some embodiments, thebrightness of a user interface (e.g., first flashlight user interface630) is represented by the total lumen output of display 602 at aparticular time. The total lumen output is a measure of the totalquantity of visible light emitted by display 602 (e.g., the total power(e.g., joules per second) of the light output by display 602, weightedbased on a model of the spectral response of the human eye). The bottomof scale 660 represents a minimum total lumen output 660 _(MIN) (e.g.,the minimum operational lumen output of display 602), and the top of thescale represents a maximum total lumen output 660 _(MAX) (e.g., themaximum operational lumen output of display 602).

As indicated by scale 660, first flashlight user interface 630 has afirst total lumen output 661 less than maximum total lumen output 660_(MAX) and greater than minimum total lumen output 660 _(MIN). With theexception of indication of time 634 and flashlight style indicia 632,first flashlight user interface 630 is substantially uniform overdisplay 602 such that the intensity (e.g., luminance or lumen per unitarea) and color of first flashlight user interface 630 are substantiallyuniform over display 602. In some embodiments, first flashlight userinterface 630 serves as an initial interface for the flashlight mode toindicate that device 600 has entered the flashlight mode, to provideinformation about the flashlight mode (e.g., the number of availableflashlight styles) and/or other common information (e.g., time), and toprovide capability for the user to adjust characteristics of theflashlight mode (e.g., the capability to change the flashlight styleand/or adjust visual characteristics of the flashlight mode). In someembodiments, the first flashlight user interface 630 is thereforeintended primarily for user interaction, and as such, has a reducedbrightness that is comfortable for a user to view instead of anincreased brightness that might be more effective for serving as aflashlight. Optionally, the brightness of first flashlight userinterface 630 is based on a brightness setting of device 600 or anamount of ambient light detected by a light sensor of device 600 (e.g.,first total lumen output 661 is directly proportional to the amount ofambient light).

Referring again to FIG. 6E, the flashlight mode operates according to afirst flashlight style, referred to herein as a constant flashlightstyle, in which the total lumen output is substantially constant overtime (e.g., the intensity is substantially uniform over display 602 andconstant over time) and the user interface is substantially white overthe entire display 602. In one example of the constant flashlight style,the total lumen output 661 of first flashlight user interface 630 issubstantially constant over a first period of time that first flashlightinterface 630 is displayed.

While first flashlight user interface 630 is displayed, device 600determines whether brightness change criteria are met. In someembodiments, the brightness change criteria are met if first flashlightuser interface 630 has been continuously displayed for greater than orequal to a predetermined threshold amount of time (e.g., three seconds).In some embodiments, the brightness change criteria are met if firstflashlight user interface 630 has been continuously displayed forgreater than or equal to the predetermined threshold amount of timewithout an intervening input (e.g., a press or rotation of rotatableinput mechanism 604, a press of input mechanism 606, a horizontal swipeon display 602 to change the flashlight style (as described in greaterdetail below), or a vertical (e.g., downward) swipe on display 602 todisplay dismiss affordance 631 and/or dismiss the flashlight mode (asalso described in greater detail below)). In some embodiments, thebrightness change criteria are met if device 600 detects an input (e.g.,a touch gesture on display 602, rotation of rotatable input mechanism604, and/or a change in orientation of device 600) while displayingfirst flashlight user interface 630.

In some embodiments, in accordance with a determination that thebrightness change criteria are not met, device 600 maintains firstflashlight user interface 630. In accordance with a determination thatthe brightness change criteria are met, device 600 displays secondflashlight user interface 640 shown in FIG. 6F. As indicated bybrightness scale 660, second flashlight user interface 640 has a secondtotal lumen output 662 greater than first total lumen output 661 offirst flashlight user interface 630. In some embodiments, second totallumen output is maximum total lumen output 660 _(MAX). Similar to firstflashlight user interface 630, the intensity and color of secondflashlight user interface 640 are substantially uniform over display602. In some embodiments, the color of second flashlight user interface640 is substantially the same as the color of first flashlight userinterface 630. Since total lumen output 662 of second flashlight userinterface 640 is greater than total lumen output 661 of first flashlightuser interface 640, however, the intensity (e.g., luminance) of secondflashlight user interface 640 is greater than the intensity of firstflashlight user interface 630.

In some embodiments, indication of time 634, flashlight style indicia632, and current style indicator 633 are not included on secondflashlight user interface 640 (e.g., they are removed from display 602when the brightness change criteria are met), as shown in FIG. 6F.Optionally, any other additional features displayed on first flashlightuser interface 630 are not included on second flashlight user interface640. Accordingly, in some embodiments, when the brightness changecriteria are met, display 602 transitions to an interface intendedprimarily for illuminating the surrounding environment by increasing thebrightness of display 602 and removing any extraneous graphicalfeatures. Optionally, second flashlight user interface 640 is maintaineduntil further input is detected.

Device 600 also maintains the current flashlight style when ittransitions to second flashlight user interface 640 from firstflashlight user interface 630. The flashlight mode operates according tothe constant flashlight style such that the total lumen output of secondflashlight user interface 640 is substantially constant (e.g., the totallumen output remains substantially at second total lumen output 662 overa period of time) and second flashlight user interface 640 issubstantially white over the entire display 602. Thus, according to theconstant flashlight style, the total lumen output is substantiallyconstant at the first total lumen output 661 while displaying firstflashlight user interface 630 and is also substantially constant at thesecond total lumen output 662 while displaying second flashlight userinterface 640.

Referring now to FIGS. 6G-6J, in some embodiments, device 600 switchesbetween first flashlight user interface 630 and second flashlight userinterface 640 based at least in part on the orientation of device 600.In some embodiments, the brightness change criteria includes anorientation detection criterion that is met by detecting a change inorientation of device 600 and/or an orientation value criterion that ismet when the orientation of device 600 is a predetermined orientation.In some embodiments, the brightness change criteria are met if at leastone of the detection change criterion and the orientation valuecriterion is met. In some embodiments, the brightness change criteriaare met only if both the detection change criterion and the orientationvalue criterion are met.

FIGS. 6G-6H illustrate views of device 600 in a first orientation.Device 600 is shown on the wrist of a user such that the firstorientation corresponds to an orientation in which display 602 is facingtoward the user. FIGS. 6I-6J illustrate views of device 600 in a secondorientation. Compared to FIGS. 6G-6H, the user's wrist has been turnedto rotate device 600 approximately 180 degrees around axis 670 so thatdisplay 602 is turned upside down (compared to the first orientation)and faces away from the user. FIG. 6I includes a pop-out view showingdevice 600 in the second orientation from a perspective looking towardthe user.

In some embodiments, device 600 detects the change in orientation ofdevice 600 from the first orientation to the second orientation, and thesecond orientation is a predetermined orientation. Accordingly, theorientation detection criterion and the orientation value criterion ofthe brightness change criteria are met. In the embodiment illustrated inFIGS. 6G-6J, the brightness change criteria are met if both theorientation detection criterion and orientation value criterion are met.As a result, in response to determining that both the orientationdetection criterion and orientation value criterion are met, device 600switches from displaying first flashlight user interface 630 todisplaying second flashlight user interface 640.

Optionally, the predetermined orientation is set to an orientation thatindicates that display 602 is pointed away from the user and/or islikely being used to illuminate the surrounding environment (e.g.,display 602 is facing downward). In some embodiments, a user specifiesan orientation in which device 600 is intended to be worn (e.g., rightwrist with rotatable input mechanism on the right). Optionally, thepredetermined orientation is based on the user-specified orientation(e.g., the specified orientation determines the orientations in whichdisplay 602 is facing toward and away from the user). Optionally, thepredetermined orientation is based on the orientation of the device atthe time of entering the flashlight mode. Optionally, there is aplurality of predetermined orientations or one or more ranges ofpredetermined orientations covering a range of orientations (e.g., arange of orientations in which the display is likely to be pointed awayfrom the user's view). In some embodiments, the orientation valuecriterion is met if the orientation of the device is any one of theplurality of predetermined orientations or falls within the one or moreranges of predetermined orientations.

As mentioned, in some embodiments, the second total lumen output 662 isintended for illuminating the surrounding environment but isuncomfortable for a user to view. In some embodiments in which thebrightness criteria are met if the first flashlight user interface iscontinuously displayed for a predetermined amount of time, thepredetermined amount of time provides the user with an opportunity toprovide an input or direct display 602 away from view before thebrightness is increased. Optionally, the brightness increase criteriaare met if the first flashlight user interface is continuously displayedfor a predetermined amount of time or if the orientation detectioncriterion and/or the orientation value criterion are met, which allows auser to bypass the delay of the predetermined amount of time byre-orienting device 600 to the predetermined orientation before thepredetermined amount of time has passed. In some embodiments, thebrightness increase criteria are met only if the orientation detectioncriterion and the orientation value criterion are met in order to reducethe chance that the brightness is increased while the user is viewingdisplay 602.

Referring now to FIG. 6K, while displaying second flashlight userinterface 640, device 600 detects input 652 (e.g., a touch gesture) ondisplay 602. In other examples, input 652 is an input on rotatable inputmechanism 604 or input mechanism 606. In some embodiments, device 600determines whether device 600 is oriented in a predeterminedinterface-lock orientation that prohibits device 600 from responding toinputs on display 602 or from being switched out of second flashlightuser interface 640. In one example, the interface-lock orientation is anorientation associated with display 602 of device 600 facing away from auser, as shown, for example, in FIGS. 6I-6J. Optionally, theinterface-lock orientation is included in a plurality of orientationsand/or ranges of orientations that prohibit device 600 from respondingto inputs on display 602 or being switched out of second flashlight userinterface 640. In some embodiments, the orientations that cause thesecond flashlight user interface 640 to be locked are different than theorientations that meet the orientation value criterion of the increasebrightness criteria.

In accordance with a determination that device 600 is oriented in theinterface-lock orientation, device 600 maintains display of secondflashlight user interface 640 in response to detecting input 652 (e.g.,device 600 does not respond to input 652). In accordance with adetermination that device 600 is not oriented in the lock-interfaceorientation, device 600 replaces second flashlight user interface 640with first flashlight user interface 630 in response to detecting input652, as shown in FIG. 6L. Returning to first flashlight user interface630 reduces the brightness of display 602 and provides indication oftime 634 and flashlight style indicia 632.

As an alternative (or in addition) to input 652, device 600 optionallyswitches from second flashlight user interface 640 to first flashlightuser interface 630 in response to detecting a change in orientation ofdevice 600 to a predetermined reduce-brightness orientation. In oneexample, while displaying second flashlight user interface 640, device600 detects a change in orientation (e.g., to the orientation shown inFIGS. 6G-6H) and determines whether the new orientation corresponds to apredetermined reduce-brightness orientation. In response to detectingthe change in orientation and determining that the new orientationcorresponds to a predetermined reduce-brightness orientation, device 600replaces second flashlight user interface 640 with first flashlight userinterface 630. Accordingly, in some embodiments in which display 602 isfacing the user when in the reduce-brightness orientation, device 600automatically reduces the brightness of display 602 in response todisplay 600 being re-oriented toward the user (e.g., in response to awrist raise motion by the user to view display 602). Optionally, afterdevice 600 has returned to first flashlight user interface 630, device600 again determines whether the brightness increase criteria are met,and if so, increases the brightness again by displaying secondflashlight user interface 640 as described above. In this way, device600 can switch back and forth between relatively bright and dim lightoutput in accordance with the user's input.

Referring now to FIG. 6M, while in first flashlight user interface 630,device 600 detects input 653 (e.g., left swipe on display 602) forchanging the style of the flashlight mode. In response to input 653,device 600 ceases operating according to the first flashlight style(e.g., the constant flashlight style) and begins operating according toan adjacent second flashlight style in the sequence of flashlightstyles. FIG. 6N illustrates one embodiment of a transition between thefirst flashlight style and the second flashlight style in which adisplay of screen 635 (representing the current flashlight style) istranslated to the left (e.g., in the same direction as input 653) offthe left edge of display 602 and screen 636 (representing the secondflashlight style) is translated onto display 602 from the right edge ofdisplay 602. Flashlight style indicia 632 is also updated (as shown inFIG. 6O). In particular, current style indicator 633 is moved from dot632-1 corresponding to the first flashlight style and is displayed atdot 632-2 corresponding to the second flashlight style. Optionally,device 600 switches flashlight styles in response to input while insecond flashlight user interface 640 in a manner analogous to thatdescribed above for first flashlight user interface 630, but withoutdisplaying and updating flashlight style indicia 632. In someembodiments, in response to detecting input for changing the flashlightstyle in second flashlight user interface 640, device changes theflashlight style and switches to first flashlight user interface 630.

The second flashlight style provides a blinking or pulsing effect byalternating between two different total lumen outputs (e.g., a highbrightness state and a low brightness state). The second flashlightstyle is referred to herein as the pulsed flashlight style, which may beused, for example, as a safety light (e.g., a light that signals thepresence of the user to others). FIG. 6O illustrates an example of theflashlight mode operating according to the pulsed flashlight style. Morespecifically, FIG. 6O illustrates the pulsed flashlight style as appliedto first flashlight user interface 630. To illustrate the pulsingeffect, FIG. 6O shows first flashlight user interface 630 at twodifferent times during operation of device 600 according to the pulsedflashlight style. Screen 637 shown on the left side of FIG. 6Orepresents first flashlight user interface 630 at a first time in a“high brightness” or “ON” state, and screen 638 shown on the right sideof FIG. 6O represents first flashlight user interface 630 at a secondtime in a “low brightness” or “OFF” state. At both times, firstflashlight user interface 630 is substantially uniform in color andintensity (e.g., except for indication of time 634 and flashlight styleindicia 632). At the first time, consistent with first flashlight userinterface 630 in the constant flashlight style, the total lumen outputis first total lumen output 661. In some embodiments, the total lumenoutput of screen 637 is different than the total lumen output associatedwith the first flashlight user interface 630 in the constant flashlightstyle, but still less than maximum total lumen output 660 _(MAX) andgreater than minimum total lumen output 660 _(MIN). At the second time,the total lumen output 663 is less than first total lumen output 661(e.g., the total lumen output is at or near minimum total lumen output660 _(MIN)). According to the pulsed flashlight style, device 600alternates back and forth between screen 637 and screen 638automatically over time. In some embodiments, device alternates betweenscreen 637 and screen 638 according to a pattern over time defined bywhen and how long each of screens 637 and 638 is displayed over time.

FIG. 6P illustrates the pulsed flashlight style as applied to secondflashlight user interface 640. The operation of the pulsed flashlightstyle as applied to second flashlight user interface 640 is the same asapplied to first flashlight user interface 630 except for the totallumen output. At a first time, consistent with second flashlight userinterface 640 in the constant flashlight style, screen 641 is displayedwith second total lumen output 662. In some embodiments, the total lumenoutput of screen 641 is different than the total lumen output associatedwith the second flashlight user interface 640 in the constant flashlightstyle, but still greater than the total lumen output associated with thefirst flashlight user interface 630 in the pulsed flashlight style(e.g., greater than total lumen output 661). At a second time, screen642 is displayed with a total lumen output 664 that is less than thetotal lumen output of screen 641 (e.g., the total lumen output is at ornear minimum total lumen output 660 _(MIN)). In some embodiments of thepulsed flashlight style, the total lumen output of first flashlight userinterface 630 in the low brightness (e.g., OFF) state is the same as thetotal lumen output of second flashlight user interface 640 in the lowbrightness state. In some embodiments of the pulsed flashlight style,the total lumen output of first flashlight user interface 630 in the lowbrightness state is different than the total lumen output of secondflashlight user interface 640 in the low brightness state. In someembodiments of the pulsed flashlight style, the pattern (e.g.,frequency) according to which device 600 alternates between the highbrightness and low brightness states (e.g., ON and OFF) is the same inboth first flashlight user interface 630 and second flashlight userinterface 640. In some embodiments of the pulsed flashlight style, thepattern according to which device 600 alternates between the highbrightness and low brightness states in first flashlight user interface630 is different than in second flashlight user interface 640.

Referring now to FIGS. 6Q-6S, while displaying first flashlight userinterface 630 in the pulsed flashlight style, device 600 detects input654 (e.g., a left swipe) on display 602, and in response, changesoperation of the flashlight mode from the second flashlight style to athird flashlight style in the sequence of flashlight styles. FIG. 6Rillustrates a transition from the second flashlight style to the thirdflashlight style analogous to the transition between the firstflashlight style and the second flashlight style described above withreference to FIGS. 6M-60. Screen 636 (again representing the secondflashlight style) translates to the left off the left edge of display602 and screen 639 (representing the third flashlight style) translatesonto display 602 from the right edge of display 602. Flashlight styleindicia 632 are updated to reflect that the third flashlight style isthe current style.

FIGS. 6S and 6T illustrate the operation of the flashlight modeaccording to the third flashlight style while displaying firstflashlight user interface 630 and second flashlight user interface 640,respectively. Similar to the constant flashlight style, the total lumenoutput of the respective flashlight user interface is substantiallyconstant over time (e.g., the display does not noticeably pulse or flashas in the second flashlight style). The intensity and color are uniformover display 602 and also substantially constant over time. However, thecolor of the interface in the third flashlight style is different thanthe color of the interface in the constant flashlight style (e.g., thecolor is not substantially white). Accordingly, the third flashlightstyle is referred to herein as the color flashlight style. In someembodiments, the color of the interface according to the colorflashlight style is limited to a relatively narrow range of wavelengths(e.g., the color is substantially red, substantially blue, substantiallygreen, or substantially yellow). The pattern on display 602 shown inFIGS. 6S-6T indicates that the color of the interface of the illustratedembodiment of the third flashlight style is red. Red may be aparticularly advantageous color for illuminating the surroundingenvironment and improving the visibility of the display at night. Aswith the other flashlight styles described above, the color flashlightstyle is consistent between first flashlight user interface 630 andsecond flashlight user interface 640. The color is substantially thesame for first flashlight user interface 630 and second flashlight userinterface 640, while the total lumen output 666 for second flashlightuser interface 640 is greater than the total lumen output 665 for firstflashlight user interface 630.

FIGS. 6U-6Y illustrate another embodiment of a transition betweenflashlight styles. Input 655 is a contact (e.g., a finger contact) ondisplay 602 that begins at position 655-1 and is maintained while movingto position 655-2. In response to movement of contact 655 from position655-1 to position 655-2, device 600 reduces in size and/or translates tothe left screen 635 (representing the first flashlight style) anddisplays screen 636 (representing the second flashlight style)translating onto display 602 from the right edge of display 602.Compared to the transition described with reference to FIGS. 6M-6N,screen 636 representing the second flashlight style is reduced in size.While still maintained, contact 655 moves to position 655-3 further tothe left on display 602. In response to the further movement of contact655 to position 655-3, screen 635 representing the first flashlightstyle is reduced in size and moved partially off the left side ofdisplay 602, screen 636 representing the second flashlight style ismoved to the center of display 602 and increased in size, and screen 639representing the third flashlight style is moved onto display 602 and ispartially displayed at a reduced size on the right edge of display 602.As shown in FIG. 6W, the representation of the second flashlight styleis in the center of display 602 and adjacent flashlight styles in thesequence of flashlight styles are represented by partially displayedsmaller screens adjacent to the representation of the second flashlightstyle. Optionally, device 600 displays affordance 671 for dismissing therepresentations of the flashlight styles and resuming operationaccording to the current flashlight style (e.g., without changing theflashlight style). At this point, in some embodiments, contact 655 isceased and a flashlight style is selected in response to input (e.g., atap) selecting the corresponding representation of the style. In someembodiments, contact 655 is ceased and device 600 removes therepresentations of the flashlight styles and operates the flashlightmode according to the flashlight style represented in the center ofdisplay 602 at the time contact 655 is ceased (e.g., the secondflashlight style). Alternatively, in response to further movement ofcontact 655 to position 655-4, screen 636 is reduced in size and movedto the left side of display 602 and screen 639 is moved to the center ofdisplay 602 and increased in size, as shown in FIG. 6X. Optionally, whencontact 655 is ceased, device 600 removes the representations of theflashlight styles and operates the flashlight mode according to thethird flashlight style (e.g., as shown in FIG. 6Y) since it isrepresented in the center of display 602 at the time contact 655 isceased. Alternatively, when contact 655 is ceased, device 600 maintainsthe representations of the flashlight styles and a flashlight style isselected in response to input (e.g., a tap) selecting the correspondingrepresentation of the style. In some embodiments, transition back to thesecond or first flashlight style is performed and displayed in ananalogous way (e.g., by swiping to the right).

Referring now to FIGS. 6Z-6AC, in some embodiments, one or more visualcharacteristics of the flashlight mode are adjusted in response to userinput. In FIG. 6Z, while displaying second flashlight user interface640, device 600 detects rotation 656 of rotatable input mechanism 604.In response, device 600 adjusts the brightness of second flashlight userinterface 640. Scale 660 in FIGS. 6Z-6AA indicates that rotation 656reduces the total lumen output of second flashlight user interface 640from output 667 to output 668. In some embodiments, the brightness isincreased in response to rotation of rotatable input mechanism 604 in adirection opposite the direction of rotation 656. Optionally, the amountof adjustment is proportional to the amount of rotation. In someembodiments, rotation 656 is detected while displaying first flashlightuser interface 630, and in response, device 600 adjusts the total lumenoutput of first flashlight user interface 630. Optionally, device 600adjusts a brightness associated with the flashlight mode in response toother types of input. In some embodiments, device 600 adjusts abrightness associated with the first, second, and/or third flashlightstyle.

In some embodiments, a visual characteristic other than brightness isadjusted in response to user input. In one example, device 600 adjusts apulse characteristic associated with the pulsed flashlight style inresponse to user input (e.g., rotation 656). Exemplary pulsecharacteristics include, but are not limited to, the pulse repetitionfrequency at which device 600 alternates between the high brightnessstate and low brightness state and the relative duration of the highbrightness state compared to the low brightness state within a cycle(e.g., duty cycle). In another embodiment, device 600 adjusts a color ofthe first and/or second flashlight user interface in response to userinput (e.g., rotation 656). In one example, device 600 adjusts thedisplay color associated with the first, second, and/or third flashlightstyle. In some embodiments, the visual characteristic that is adjustedis based on the current flashlight style in which the flashlight mode isoperating (e.g., while operating in the first flashlight style, totallumen output is adjusted; while operating in the second flashlightstyle, a pulse characteristic is adjusted; and while operating in thethird flashlight style, a color is adjusted).

Referring now to FIGS. 6AB-6AC, while operating in the flashlight mode,device 600 detects contact 657 on display 602 and determines acharacteristic intensity of contact 657. Optionally, in accordance witha determination that the characteristic intensity of contact 657 doesnot exceed a threshold characteristic intensity, device 600 performs oneor more of the operations described above (e.g., switches display 602between first flashlight user interface 630 and second flashlight userinterface 640). In some embodiments, in accordance with a determinationthat the characteristic intensity of contact 657 exceeds a thresholdcharacteristic intensity, device 600 adjusts a visual characteristic ofthe flashlight mode as described above (e.g., device 600 increases ordecreases the total lumen output or pulse repetition frequency orchanges a display color associated with the flashlight mode). As shownin FIG. 6AC, device 600 changes the color of display 602, as representedby the change in pattern shown on display 602 in FIG. 6AC.

In other embodiments, in accordance with a determination that thecharacteristic intensity of the contact exceeds a thresholdcharacteristic intensity, device 600 enables a capability to adjust avisual characteristic (e.g., device 600 enables a capability to adjust avisual characteristic in response to a rotation and/or press ofrotatable input mechanism 604, a press of input mechanism 606, and/or atouch input on display 602). In some embodiments, in accordance with adetermination that the characteristic intensity of the contact exceeds athreshold characteristic intensity, device 600 displays a menu forselecting a visual characteristic of the flashlight mode (e.g., a menuof available colors for the third flashlight style). In suchembodiments, device 600 adjusts a visual characteristic of theflashlight mode in response to selection of an item (e.g., anaffordance) in the menu.

Referring now to FIGS. 6AD-6AG, device 600 provides an easy andefficient technique for dismissing the flashlight mode. While operatingin the flashlight mode (e.g., while displaying first flashlight userinterface 630, as shown, for example, in FIG. 6AD), device 600 detectsinput 658 (e.g., a tap and downward drag or downward swipe gesture). Inresponse to input 658, device 600 displays dismiss affordance 631 fordismissing the flashlight mode at the top of display 602. In someembodiments, device 600 ceases to display dismiss affordance 631 andre-displays indication of time 634 if dismiss affordance 631 iscontinuously displayed for a predetermined amount of time. In responseto further input 659 corresponding to selection of dismiss affordance631 (e.g., further downward dragging of the same contact 658 or aseparate tap and drag or swipe gesture beginning on or near dismissaffordance 631), device 600 dismisses the flashlight mode. Dismissingthe flashlight mode includes ceasing to operate device 600 according tothe flashlight mode. FIG. 6AF illustrates an exemplary embodiment of ananimated transition for dismissing the flashlight mode. The firstflashlight user interface 630 is translated downward off the bottom ofdisplay 602 and user interface 610 including watch face 611 is displayed(e.g., revealed), as shown in FIG. 6AG. In some embodiments, upondismissing the flashlight mode, device 600 displays an applicationspringboard, or returns to the user interface from which the flashlightmode was entered (e.g., Control Center interface 620).

FIGS. 7A-7D illustrate a flow diagram illustrating a method forproviding and operating a flashlight mode using an electronic device inaccordance with some embodiments. Method 700 is performed at a device(e.g., 100, 300, 500, or 600) with a display. Optionally, the display isa touch-sensitive display. Optionally, the device includes anorientation sensor. Some operations in method 700 are, optionally,combined, the order of some operations is, optionally, changed, and someoperations are, optionally, omitted.

As described below, method 700 provides an intuitive way for providing aflashlight mode on the display of the device. The method reduces thecognitive burden on a user for accessing and operating the flashlightmode, thereby creating a more efficient human-machine interface. Forbattery-operated computing devices, enabling a user to operate aflashlight mode faster and more efficiently conserves power andincreases the time between battery charges.

At block 702, the device detects a first input (e.g., 651) whiledisplaying a first user interface (e.g., 620) on the display. In someembodiments, the input is on the display.

At block 704, in response to detecting the first input on the display,the device enters a flashlight mode (e.g., FIGS. 6B-6E). At block 706,entering the flashlight mode includes replacing the first user interfacewith a first flashlight user interface (e.g., 630) having a first totallumen output (e.g., 661) and a first luminance that is substantiallyuniform over the display. Replacing the first user interface with afirst flashlight user interface that has a luminance that issubstantially uniform over the display provides the user with feedbackthat the device has changed modes and that the entered mode is aflashlight mode. Providing improved visual feedback to the user enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently. Also, as will be described with reference to block 720below, the first total lumen output is less than a second total lumenoutput of a second flashlight user interface that is subsequentlydisplayed. The greater brightness of the second lumen output is intendedfor illuminating the surrounding environment and may be uncomfortable oreven harmful to view. Displaying the first flashlight user interfacewith the first total lumen output provides the user with an opportunityto avoid discomfort by looking away from the display or pointing thedisplay away from the user's view before the brightness increases.

In some embodiments, the flashlight mode includes at least a firstflashlight style (e.g., constant flashlight style) and a secondflashlight style (e.g., pulsed flashlight style or color flashlightstyle). Optionally, the first flashlight user interface includes indicia(e.g., 632) of a sequence of styles that includes at least the firstflashlight style and the second flashlight style and an indication(e.g., 633) of a current style according to which the flashlight mode isoperating. Displaying the indicia of the sequence of styles and theindication of the current style provides the user with feedback thatmultiple flashlight styles are available and which style is currentlyimplemented. The potential benefits of providing visual feedback aredescribed above.

Optionally, at block 708, the device maintains the first total lumenoutput substantially constant over time (e.g., in accordance with thefirst flashlight style, the first total lumen output is substantiallyconstant over time). Keeping the first total lumen output substantiallyconstant over time provides the user with feedback that the flashlightmode supplies a constant source of light for effectively and efficientlyilluminating the surrounding environment. Optionally, at block 710, thedevice alternates the first flashlight user interface between the firsttotal lumen output and a third total lumen output (e.g., in accordancewith the second flashlight style shown in FIGS. 60-6P). Alternating thefirst flashlight user interface between the first total lumen output anda third total lumen output provides the user with feedback that theflashlight mode supplies a pulsed or flashing source of light, which maybe effective for illuminating the surrounding environment and/or servingas a safety feature to draw attention to the device, and thus, the user.Optionally, at block 712, the device displays the first flashlight userinterface with a substantially uniform color across the interface (e.g.,in accordance with a third flashlight style shown in FIGS. 6S-6T).Displaying the first flashlight user interface with a substantiallyuniform color across the interface provides the user with furtherfeedback that the device is operating in a flashlight mode and that theflashlight mode supplies illumination of the displayed color.

Optionally, at block 714, the device detects a change in orientation ofthe device from a first orientation (e.g., FIGS. 6G-6H) to a secondorientation (e.g., FIGS. 6I-6J).

At block 716, the device determines whether brightness change criteriaare met. In some embodiments, the brightness change criteria includes afirst criterion that is met by detecting the change in orientation and asecond criterion that is met when the second orientation is a firstpredetermined orientation. In some embodiments, the brightness changecriteria are met if the first flashlight user interface has beencontinuously displayed for greater than a predetermined threshold amountof time.

Optionally, at block 718, in accordance with a determination that thebrightness change criteria are not met, the device maintains the firstflashlight user interface.

At block 720, in accordance with a determination that the brightnesschange criteria are met, the device displays a second flashlight userinterface (e.g., 640). The second flashlight user interface has a secondtotal lumen output (e.g., 662) greater than the first total lumen outputand a second luminance that is substantially uniform over the display.Displaying the second flashlight user interface with a second totallumen output greater than the first total lumen output provides the userwith a greater amount of light to more effectively illuminate thesurrounding environment and/or draw attention to the device. Displayingthe second flashlight user interface with a luminance that issubstantially uniform over the display improves the efficiency of theflashlight mode since the entire display is devoted to providingillumination. Displaying the second flashlight user interface inaccordance with the determination that the brightness change criteriaare met provides the user with an opportunity to recognize that thedevice has entered the flashlight mode before the second user interfaceis display (as mentioned) and provides increased control over theflashlight mode. In the case of the brightness change criteria being metif the first flashlight user interface has been continuously displayedfor greater than a predetermined threshold amount of time, the secondflashlight user interface is displayed automatically when a set ofconditions has been met without requiring further user input, whichreduces the number of inputs needed to increase the brightness of thedisplay. Performing an operation when a set of conditions has been metwithout requiring further user input and reducing the number of inputsneeded to perform an operation enhance the operability of the device andmake the user-device interface more efficient (e.g., by helping the userto provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently. Also, since the firstflashlight user interface has a reduced brightness, automatic activationof the second flashlight user interface provides the user with feedbackthat a greater brightness level is available. The advantages ofproviding improved visual feedback are described above.

Optionally, at block 722, the device maintains the second total lumenoutput substantially constant over time (e.g., in accordance with thefirst flashlight style (e.g., the constant flashlight style), the secondtotal lumen output is substantially constant over time). Keeping thesecond total lumen output substantially constant over time provides theuser with a constant source of light with increased brightness foreffectively and efficiently illuminating the surrounding environment.Optionally, at block 724, the device alternates the second flashlightuser interface between the second total lumen output and a fourth totallumen output (e.g., in accordance with the second flashlight style(e.g., pulsed flashlight style shown in FIGS. 60-6P)). Alternating thesecond flashlight user interface between the second total lumen outputand a fourth total lumen output (e.g., 664) provides the user with apulsed or flashing source of light, which may be effective forilluminating the surrounding environment and/or serving as a safetyfeature to draw attention to the device, and thus, the user. Optionally,at block 726, the device displays the second flashlight user interfacewith the substantially uniform color across the interface (e.g., inaccordance with the third flashlight style (color flashlight style shownin FIGS. 6S-6T)). Displaying the second flashlight user interface with asubstantially uniform color across the interface provides the user withillumination of the displayed color at an increased brightness.

Optionally, at blocks 728 and 730, the device detects a second input(e.g., 652) while displaying the second flashlight user interface, andin response to detecting the second input, replaces the secondflashlight user interface with the first flashlight user interface(e.g., FIGS. 6K-6L). Replacing the second flashlight user interface withthe first flashlight user interface in response to an input provides theuser with the additional control of the flashlight mode by providing theability to reduce the brightness of the display without exiting theflashlight mode. Providing the ability to reduce the brightness of thedisplay without exiting the flashlight mode enhances the operability ofthe device and makes the user-device interface more efficient, thebenefits of which are described above. Also, reducing the brightness ofthe display may make the display more comfortable to view while, forexample, checking the time (e.g., via indication of time 634) orswitching the flashlight style, or otherwise operating the device.

Optionally, at blocks 732 and 734, the device detects a third input(e.g., 652) while displaying the second flashlight user interface anddetermines whether the device is oriented in a second predeterminedorientation (e.g., the interface-lock orientation at the time the thirdinput is detected). Optionally, at block 736, in accordance with adetermination that the device is not oriented in the secondpredetermined orientation (e.g., the interface-lock orientation), thedevice replaces the second flashlight user interface with the firstflashlight user interface (e.g., in response to the third input).Optionally, at block 738, in accordance with a determination that thedevice is oriented in a second predetermined orientation, the devicemaintains display of the second flashlight user interface. Maintainingthe display of the second flashlight user interface in accordance with adetermination that the device is oriented in a second predeterminedorientation, despite the third user input, prevents the increasedbrightness of the second flashlight user interface from beinginterrupted due to inadvertent inputs when the device is orientedconsistent with an intent to illuminate the surrounding environment(e.g., with the display facing away from the user). Reducing thelikelihood of inadvertent operation enhances the operability of thedevice and makes the user-device interface more efficient, the benefitsof which are described above.

Optionally, at block 740, while the device is operating according to afirst flashlight style (and is displaying the first flashlight userinterface or the second flashlight user interface), the device detects afourth input (e.g., 653). Optionally, at block 742, in response todetecting the fourth input, the device ceases to operate according tothe first flashlight style and operates according to the secondflashlight style (e.g., FIG. 6O). Switching from the first flashlightstyle to the second flashlight style in this manner provides the userwith increased control over the flashlight mode and reduces the numberof inputs required to change the style of illumination by providing theability to change the style directly from within the flashlight mode(instead of, e.g., through a separate settings menu). The benefits ofreducing the number of inputs required to perform an operation aredescribed above.

Optionally, at block 744, the device detects a fifth input (e.g., 656)(e.g., while operating in the flashlight mode). In some embodiments, thefifth input includes a contact (e.g., 657) on the display. Optionally,at block 746, the device determines a characteristic intensity of thecontact on the display. Optionally, at block 748, in response todetecting the fifth input, the device adjusts a visual characteristic ofthe flashlight mode (e.g., FIGS. 6Z-6AC). Adjusting a visualcharacteristic of the flashlight mode while the device is operating inthe flashlight mode reduces the number of inputs needed to adjust thevisual characteristics of the illumination (e.g., the user does not haveto access a separate settings application). The benefits of reducing thenumber of inputs required to perform an operation are described above.Optionally, at block 750, the visual characteristic of the flashlightmode is adjusted in accordance with a determination that thecharacteristic intensity of the contact exceeds a thresholdcharacteristic intensity. Adjusting the visual characteristic of theflashlight mode in accordance with a determination that thecharacteristic intensity of the contact exceeds a thresholdcharacteristic intensity provides the user with the ability to adjustthe appearance of the illumination without displaying additionalgraphical user interface objects on the display. Providing additionalcontrol options without cluttering the UI with additional displayedcontrols enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

Optionally, at blocks 752, 754, and 756, the device displays, on thedisplay, an affordance (e.g., 631) for dismissing the flashlight mode,detects a user input (e.g., 659) corresponding to selection of theaffordance for dismissing the flashlight mode, and in response todetecting the user input corresponding to selection of the affordancefor dismissing the flashlight mode, dismisses the flashlight mode (e.g.,FIGS. 6AE-AG). Displaying an affordance for dismissing the flashlightmode provides the user with feedback that the flashlight mode can bedismissed with selection of the affordance. The affordance thus providesan efficient way to dismiss the flashlight mode while also reducing thechance that the user will inadvertently dismiss the flashlight mode.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

1-16. (canceled)
 17. An electronic device, comprising: a touch-sensitivesurface; a display; one or more processors; and memory storing one ormore programs configured to be executed by the one or more processors,the one or more programs including instructions for: while operating ina flashlight mode, displaying a first flashlight user interface having afirst total lumen output and a first luminance that is substantiallyuniform over the display; while displaying the first flashlight userinterface, detecting, via the touch-sensitive surface, a swipe gesture;and in response to detecting the swipe gesture and in accordance with adetermination that the swipe gesture is in a first direction, dismissingthe flashlight mode, wherein dismissing the flashlight mode includesceasing to display the first flashlight user interface.
 18. Theelectronic device of claim 17, wherein dismissing the first flashlightmode includes displaying a watch face user interface on the display. 19.The electronic device of claim 17, the one or more programs furtherincluding instructions for: while displaying a control center userinterface, detecting an input that corresponds to activation of anobject of the control center user interface, wherein the control centeruser interface is different from the watch face user interface; inresponse to detecting the input that corresponds to activation of theobject, entering the flashlight mode and displaying the first flashlightuser interface.
 20. The electronic device of claim 17, wherein the firstflashlight user interface operates in a first flashlight style, the oneor more programs further including instructions for: in response todetecting the swipe gesture and in accordance with a determination thatthe swipe gesture is in a second direction different from the firstdirection, transitioning from the first flashlight user interfaceoperating in the first flashlight style to a second flashlight userinterface operating in a second flashlight style that is different fromthe first flashlight style.
 21. The electronic device of claim 20,wherein transitioning from the first flashlight user interface to thesecond flashlight user interface includes concurrently displaying: atleast a portion of the first flashlight user interface operating in thefirst flashlight style; and at least a portion of the second flashlightuser interface operating in the second flashlight style.
 22. Theelectronic device of claim 20, wherein transitioning from the firstflashlight style to the second flashlight style includes displaying thesecond flashlight user interface having a second total lumen output thatis less than the first total lumen output of the first flashlight userinterface.
 23. The electronic device of claim 17, the one or moreprograms further including instructions for: in response to detecting afirst portion of the swipe gesture in the first direction, displaying,on the display, an indication corresponding to dismissing the flashlightmode.
 24. A non-transitory computer-readable storage medium storing oneor more programs configured to be executed by one or more processors ofan electronic device with a display and a touch-sensitive surface, theone or more programs including instructions for: while operating in aflashlight mode, displaying a first flashlight user interface having afirst total lumen output and a first luminance that is substantiallyuniform over the display; while displaying the first flashlight userinterface, detecting, via the touch-sensitive surface, a swipe gesture;and in response to detecting the swipe gesture and in accordance with adetermination that the swipe gesture is in a first direction, dismissingthe flashlight mode, wherein dismissing the flashlight mode includesceasing to display the first flashlight user interface.
 25. Thenon-transitory computer-readable storage medium of claim 24, whereindismissing the first flashlight mode includes displaying a watch faceuser interface on the display.
 26. The non-transitory computer-readablestorage medium of claim 24, the one or more programs further includinginstructions for: while displaying a control center user interface,detecting an input that corresponds to activation of an object of thecontrol center user interface, wherein the control center user interfaceis different from the watch face user interface; in response todetecting the input that corresponds to activation of the object,entering the flashlight mode and displaying the first flashlight userinterface.
 27. The non-transitory computer-readable storage medium ofclaim 24, wherein the first flashlight user interface operates in afirst flashlight style, the one or more programs further includinginstructions for: in response to detecting the swipe gesture and inaccordance with a determination that the swipe gesture is in a seconddirection different from the first direction, transitioning from thefirst flashlight user interface operating in the first flashlight styleto a second flashlight user interface operating in a second flashlightstyle that is different from the first flashlight style.
 28. Thenon-transitory computer-readable storage medium of claim 27, whereintransitioning from the first flashlight user interface to the secondflashlight user interface includes concurrently displaying: at least aportion of the first flashlight user interface operating in the firstflashlight style; and at least a portion of the second flashlight userinterface operating in the second flashlight style.
 29. Thenon-transitory computer-readable storage medium of claim 27, whereintransitioning from the first flashlight style to the second flashlightstyle includes displaying the second flashlight user interface having asecond total lumen output that is less than the first total lumen outputof the first flashlight user interface.
 30. The non-transitorycomputer-readable storage medium of claim 24, the one or more programsfurther including instructions for: in response to detecting a firstportion of the swipe gesture in the first direction, displaying, on thedisplay, an indication corresponding to dismissing the flashlight mode.31. A method, comprising: at an electronic device with a display and atouch-sensitive surface: while operating in a flashlight mode,displaying a first flashlight user interface having a first total lumenoutput and a first luminance that is substantially uniform over thedisplay; while displaying the first flashlight user interface,detecting, via the touch-sensitive surface, a swipe gesture; and inresponse to detecting the swipe gesture and in accordance with adetermination that the swipe gesture is in a first direction, dismissingthe flashlight mode, wherein dismissing the flashlight mode includesceasing to display the first flashlight user interface.
 32. The methodof claim 31, wherein dismissing the first flashlight mode includesdisplaying a watch face user interface on the display.
 33. The method ofclaim 31, the method further comprising: while displaying a controlcenter user interface, detecting an input that corresponds to activationof an object of the control center user interface, wherein the controlcenter user interface is different from the watch face user interface;in response to detecting the input that corresponds to activation of theobject, entering the flashlight mode and displaying the first flashlightuser interface.
 34. The method of claim 31, wherein the first flashlightuser interface operates in a first flashlight style, the method furthercomprising: in response to detecting the swipe gesture and in accordancewith a determination that the swipe gesture is in a second directiondifferent from the first direction, transitioning from the firstflashlight user interface operating in the first flashlight style to asecond flashlight user interface operating in a second flashlight stylethat is different from the first flashlight style.
 35. The method ofclaim 34, wherein transitioning from the first flashlight user interfaceto the second flashlight user interface includes concurrentlydisplaying: at least a portion of the first flashlight user interfaceoperating in the first flashlight style; and at least a portion of thesecond flashlight user interface operating in the second flashlightstyle.
 36. The method of claim 34, wherein transitioning from the firstflashlight style to the second flashlight style includes displaying thesecond flashlight user interface having a second total lumen output thatis less than the first total lumen output of the first flashlight userinterface.
 37. The method of claim 31, the method further comprising: inresponse to detecting a first portion of the swipe gesture in the firstdirection, displaying, on the display, an indication corresponding todismissing the flashlight mode.